Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1599

reference: 524-tree-1
name: 1599
tree-preservation-order: undefined
524-tpo-1
uprn
address-text
point: POINT (-1.017272 50.898211)
geometry: MULTIPOLYGON (((-1.017186 50.898202,-1.017190 50.898219,-1.017202 50.898234,-1.017221 50.898246,-1.017244 50.898254,-1.017271 50.898257,-1.017297 50.898254,-1.017321 50.898247,-1.017340 50.898235,-1.017352 50.898220,-1.017357 50.898203,-1.017353 50.898187,-1.017341 50.898171,-1.017323 50.898159,-1.017299 50.898152,-1.017273 50.898149,-1.017246 50.898151,-1.017222 50.898159,-1.017203 50.898170,-1.017191 50.898185,-1.017186 50.898202)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL